Mulesoft

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Solutions Index

Attribute	Value
Publisher	Microsoft Corporation
Support Tier	Microsoft
Support Link	https://support.microsoft.com
Categories	DevOps,IT Operations
Version	3.1.0
Author	Microsoft - support@microsoft.com
First Published	2022-07-12
Solution Folder	Mulesoft
Marketplace	Azure Marketplace · Popularity: 🔵 Medium (68%)

The MuleSoft Cloudhub solution provides the capability to ingest logs from Cloudhub applications into Microsoft Sentinel. This solution includes two data connector options: an Azure Function-based connector using the Cloudhub API, and a push-based CCF connector that receives logs directly via Log4j HTTP appender as recommended by MuleSoft.

Underlying Microsoft Technologies used:

This solution takes a dependency on the following technologies, and some of these dependencies either may be in Preview state or might result in additional ingestion or operational costs:

a. Codeless Connector Framework (CCF)

b. Log Ingestion API

c. Data Collection Rules (DCR)

d. Azure Monitor HTTP Data Collector API

e. Azure Functions

Data Connectors: 2, Parsers: 1

Learn more about Microsoft Sentinel | Learn more about Solutions

Data Connectors
Tables Used
Content Items

Data Connectors

This solution provides 3 data connector(s):

🔶 CLv1: This connector ingests into a table that uses the legacy Custom Log V1 schema format with type-suffixed column names (e.g. _s, _d, _b, _t, _g). Note: identification is based on column name suffixes which are also permitted in CLv2, so this classification may not always be accurate.

Tables Used

This solution uses 3 table(s):

Table	Used By Connectors	Used By Content
`MuleSoftCloudhubLogs_CL`	MuleSoft CloudHub Logs (Push Connector via Codeless Connector Framework)	-
`MuleSoft_Cloudhub_CL` 🔶	MuleSoft Cloudhub	-
`MulesoftCloudhubAlerts_CL`	Mulesoft CloudHub Alerts Connector (via Codeless Connector Framework)	-

🔶 CLv1: This table uses the legacy Custom Log V1 schema format with type-suffixed column names (e.g. _s, _d, _b, _t, _g). Note: identification is based on column name suffixes which are also permitted in CLv2, so this classification may not always be accurate.

Content Items

This solution includes 1 content item(s):

Content Type	Count
Parsers	1

Parsers

Name	Description	Tables Used
MuleSoftCloudhub	-	`MuleSoftCloudhubLogs_CL` (read) `MuleSoft_Cloudhub_CL` (read) `MulesoftCloudhubAlerts_CL` (read)

Release Notes

Version	Date Modified (DD-MM-YYYY)	Change History
3.2.0	02-07-2026	Fixed Data Connectors Count issue on UI.
3.1.0	17-06-2026	Added MuleSoft CloudHub `Alerts` CCF Connector & `Logs` CCF Push Connector for real-time log streaming via Log4j HTTP appender. Updated Definition file by removing empty instructions.
3.0.2	09-09-2024	Updated the python runtime version to 3.11
3.0.1	13-06-2024	Updated Data Connector instructions to notify Cloudhub Application support.